JBoss.orgCommunity Documentation
Be aware, JBoss Communications SS7 Stack is subject to changes as it is under active development!
The JBoss Communications SS7 Stack is logically divided into two sections. The lower section includes SS7 Level 3 and below. The lower section is influenced by type of SS7 hardware (Level 1) used.
The upper section includes SS7 Level 4 and above. This logical division is widely based on flexibility of JBoss Communications SS7 Stack to allow usage of any SS7 hardware available in the market and yet JBoss Communications SS7 Stack Level 4 and above remains the same.
Further JBoss Communications SS7 Stack provides flexibility to use the Level 2,3 and Level 4 in same JVM and
in same machine where SS7 Hardware (Level 1) is installed. Or its also possible to have Level 1,2,3 to be installed
on separate machine and Level 4 on separate machine. In latter case M3UA
over SCTP
is leveraged for communication between Level 4 and Level 3 and is called JBoss Communications Signaling Gateway.
Bellow diagram shows complete JBoss Communications SS7 Stack in same machine
Bellow diagram shows JBoss Communications Signaling Gateway
If you use JBoss Communications M3UA stack, you have to use JDK 7 to run the stack as well as to compile source code. M3UA leverages Java SCTP which is available only from JDK 7.
Apart from advantages mentioned in
JBoss Communications SS7 Stack consists of following functional blocks:
Shell
is Command Line Interface (CLI) tool which allows to manage different aspects of JBoss Communications SS7 Stack in interactive manner.
It connects to different instances of JBoss Communications SS7 Stack which manage Linksets
,
SCCP
resource, routing, M3UA
and SCTP
. For detailed information please refer to: Chapter 5, Shell Command Line.
Usually Shell
will be invoked from remote machine(remote to Linksets
and application protocols).
SS7 service creates instance of JBoss Communications SCCP Stack and bind's it to JNDI name java:/mobicents/ss7/sccp
SS7 Service is JMX based service deployed in JBoss Application Server
SS7 Service hides the details like whether Level 4 and above connects to JBoss Communications Signaling Gateway via M3UA or SS7 Hardware installed in same machine as Level 4
Diagram below depicts elements which are deployed as part of
SS7 Service
:
Service serves following purposes:
Access points allows user to access lower layer protocols, like SCCP
and interact through such protocols with SS7
network.
Shell Executor
allows Shell
client to connect and issue commands.
Configuration of SS7 Service is explained in section Section 3.4, “ Configuring JBoss Communications SS7 Service ”
Diagram below depicts how JBoss Communications SS7 Stack is used:
JBoss Communications Signaling Gateway (SG) is a signaling agent that receives/sends Switched Circuit Network (SCN) native signaling at the edge of the IP network. JBoss Communications Signaling Gateway leverages JBoss Communications M3UA Stack explained in ??? and MTP
Diagram below shows the components which are included in JBoss Communications SG. Configuration of SG is explained in ???